Add accounts pool based write lock contention to banking bench #5460
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
appetrosyan
force-pushed
the
accounts-banking-bench
branch
from
5b74ceb to
915f79f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The current
banking-benchtest suite is not representative (enough) of what mainnet workloads are. Because of this, it's difficult to evaluate the scheduler before it hits a production network and even evaluating modifications is tricky.This necessitates a more comprehensive test suite.
Summary of Changes
In addtion to the
WriteLockContentionenum that currently exists, I've implemented an account-pool contention algorithm that allows for more granular contention and more representative workloads by varying the number of accounts.A quick run showed some interesting behavior that the current test suite does not of the scheduler and the greedy scheduler: